-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[ntuple] cache number of entries in reader #19877
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Test Results 21 files 21 suites 3d 18h 32m 26s ⏱️ For more details on these failures, see this check. Results for commit 1623541. ♻️ This comment has been updated with latest results. |
4d5df2e
to
1623541
Compare
@@ -82,6 +82,8 @@ private: | |||
/// Retrieving descriptor data from an RNTupleReader is supposed to be for testing and information purposes, | |||
/// not on a hot code path. | |||
std::optional<ROOT::RNTupleDescriptor> fCachedDescriptor; | |||
/// We know that the RNTupleReader is always reading a single RNTuple, so the number of entries is fixed. | |||
ROOT::NTupleSize_t fCachedNEntries = kInvalidNTupleIndex; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this default make sense? Wouldn't 0 be a more apt choice?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, maybe it's fine to just call it fNEntries
at this point?
Follow up of #19763